Allow SciMLBase v3.3+ in compat#205
Merged
ChrisRackauckas merged 1 commit intoApr 16, 2026
Merged
Conversation
SciMLBase v3.0 introduced breaking changes to AbstractVectorOfArray (sol[i] now returns scalar elements rather than timesteps, etc.). The DEN source code already uses the v3-safe patterns (sol.u, sol.stats, last(sol.u)), so no source changes are required. This commit widens the compat bound to signal readiness. SciMLBase will continue to resolve to v2.x until downstream deps (DiffEqBase, OrdinaryDiffEq) gain v3 support, at which point this bump lets the resolver pull v3 without a second compat PR. Supersedes SciML#204 (dependabot) which failed CI due to force_latest_compatible_version=true forcing SciMLBase@3.3 in a graph where RecursiveArrayTools v4 conflicts with pinned GPUArraysCore 0.1-0.2. Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Supersedes #204 (dependabot, failing CI) by applying the same
SciMLBasecompat widening ("2"→"2, 3.3") and verifying no source-level breaking changes need handling.Why #204 fails CI
julia-actions/julia-runtestsetsforce_latest_compatible_version=trueautomatically for dependabot PRs, which forces SciMLBase@3.3.0 during the test sandbox resolve. ButDiffEqBase(direct dep) still pins SciMLBase to2.143.0 - 2— there is no DiffEqBase release that supports SciMLBase v3 yet. Under forced-latest, the resolver ends up withRecursiveArrayTools v4(required by SciMLBase v3) conflicting with the pinnedGPUArraysCore = "0.1, 0.2"(which only exists for RecursiveArrayTools ≤ v3.54), so CI fails with:This PR's CI runs with
force_latest_compatible_version=false(default for non-dependabot PRs), so SciMLBase resolves to v2.155.0 and tests pass as on main today.Breaking changes in SciMLBase v3
Reviewed the v3.0.0 release notes:
sol[i]→sol.u[i]/sol[:, i]length(sol)→length(sol.u)for u in sol→for u in sol.uu_modified!→derivative_discontinuity!prob_func(prob, i, repeat)→prob_func(prob, ctx)sol.destats,.minimizer,.minimum,TimeChoiceIterator, deprecated type aliasesThe DEN source only touches solutions via
sol.u,sol.stats, andlast(sol.u)(seesrc/utils.jl:47,68), and does not use any deprecated API. So no source changes are required.Effective behavior
The compat bump is a no-op at resolve time until DiffEqBase / OrdinaryDiffEq / RecursiveArrayTools gain SciMLBase v3 support, at which point the resolver can pull v3 without another compat PR.
Test plan
Pkg.test()passes locally on Julia 1.11 (layers_tests + utils_tests, 1549 passing)🤖 Generated with Claude Code